Card-personalization system

ABSTRACT

A personalized card may be generated using a card-personalization system accessible via multiple access points on a network. In some aspects, the personalized card may include a physical card having an image selected by a user in a card-personalization process. The user may be assigned a code that may both authenticate the user to access the card-personalization system and identify a position of the user in the card-personalization process. The card-personalization process may include a selection process for selecting an image, an approval process for approving the image, and a creation process for generating the personalized card including the image.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Non-provisional applicationSer. No. 17/315,564, filed May 10, 2021, which is a continuation of U.S.Non-provisional application Ser. No. 16/538,276, filed Aug. 12, 2019,now U.S. Pat. No. 11,032,274, which is a continuation of U.S.Non-provisional application Ser. No. 15/088,483, filed Apr. 1, 2016, nowU.S. Pat. No. 10,425,406, which claims priority to U.S. ProvisionalApplication Ser. No. 62/141,559, filed Apr. 1, 2015 and titled “CardDesign Application Authentication,” the entirety of each of which ishereby incorporated by reference herein.

TECHNICAL FIELD

The present disclosure generally relates to card-personalizationsystems, and, more particularly, although not necessarily exclusively,to generating a personalized physical card using a physicalcard-personalization system having multiple access points on a network.

BACKGROUND

Online platforms may provide users access to numerous resources via theInternet and other networks. The network resources may include publicresources that are generally accessible as well as personalizedresources including sensitive information intended only for a particularcustomer. Authentication processes may be used to allow access to thepersonalized resources. For example, a user may be required to enter apassword, or other personalized information corresponding to the user,to confirm the user's identity prior to allowing access to certainnetwork resources having sensitive information. Each of the networkresources may be interconnected to allow users to navigate between thevarious public and personalized resources from different points ofaccess to each network resource. Certain personalized resources may bedirected toward sensitive information or processes that require a userto navigate to the resource multiple times over an extended period.Difficulties may arise with respect to maintaining the authentication ofthe user without requiring a user to repeatedly reenter authenticationinformation when navigating to the personalized resource from differentaccess points.

SUMMARY

In some aspects of the present disclosure, a system may include aprocessing device configured for communicating through multiple accesspoints of a network to exchange information with a user. The multipleaccess points may include a plurality of different devices and aplurality of different communication channels. The system may alsoinclude a memory device accessible to the processing device andincluding instructions executable by the processing device to cause theprocessing device to receive a code from a device of the plurality ofdifferent devices, the device being associated with the user. The memorydevice may also include instructions executable by the processing deviceto cause the processing device to access a location in memory and usethe code and user information stored at the location in the memory toauthenticate the user and determine a current step of the user in aprocess that includes a plurality of steps for personalizing a physicalcard. In some aspects, the plurality of steps may include at leastreceiving an image, or a selection of the image, from user input andassociating the image with a personalization plan for the physical card.The memory device may also include instructions executable by theprocessing device to cause the processing device to transmit the imageand the personalization plan for the physical card electronically to aprinting subsystem for generating a personalized card for the user usingthe personalization plan for the physical card.

In additional aspects of the present disclosure, a method may includereceiving a code from a user via a device of a plurality of user devicescouplable to a card-personalization system that is accessible to theplurality user devices through multiple access points of a network. Themethod may also include authenticating the user from the device byaccessing a location in a memory of the card-personalization system andcomparing the code to a stored code that is associated with the user inthe memory. The method may also include determining a current step ofthe user in a process that includes a plurality of steps forpersonalizing a physical card, the plurality of steps including at leastreceiving an image, or a selection of the image, from user input andassociating the image with a personalization plan for the physical card.The method may also include transmitting the image and thepersonalization plan for the physical card electronically to a printingsubsystem for generating a personalized card for the user using thepersonalization plan for the physical card.

In additional aspects of the present disclosure, a non-transitorycomputer-readable medium may include program code executable by aprocessing device configured for communicating through multiple accesspoints of a network to exchange information with a user. The multipleaccess points may include a plurality of different devices and aplurality of different communication channels. The program code may beexecutable by the processing device to cause the processing device togenerate a code in response to a request to personalize a physical card,the code including a random set of alphanumeric characters. The programcode may also be executable by the processing device to cause theprocessing device to transmit the code to the user via the network in anelectronic message, the electronic message including a linkcorresponding to an access point of the multiple access points. Theprogram code may also be executable by the processing device to causethe processing device to receive the code from the user via a device ofa plurality of user devices. The program code may also be executable bythe processing device to cause the processing device to authenticate theuser from the device by accessing a location in a memory and comparingthe code to a stored code that is associated with the user in thememory. The program code may also be executable by the processing deviceto cause the processing device to determine a current step of the userin a process that includes a plurality of steps for personalizing thephysical card. The plurality of steps including at least receiving animage, or a selection of the image, from user input and associating theimage with a personalization plan for the physical card.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a network environment for accessinga card-personalization system from multiple network resources accordingto some aspects of the present disclosure.

FIG. 2 is a block diagram depicting the card-personalization system ofFIG. 1 according to some aspects of the present disclosure.

FIG. 3 is a block diagram depicting an example of the database of FIG. 2according to some aspects of the present disclosure.

FIG. 4 is a flow chart depicting a process for assigning a user code forthe card-personalization system of FIG. 2 according to some aspects ofthe present disclosure.

FIG. 5 is a flow chart depicting a process for authenticating a user todesign a physical card using the card-personalization system of FIG. 2according to some aspects of the present disclosure.

FIG. 6 is an example of a user interface generated by the system of FIG.1 for receiving a user code according to some aspects of the presentdisclosure.

FIG. 7 is an example of a user interface generated by the system of FIG.1 for receiving a selection of an image according to some aspects of thepresent disclosure.

FIG. 8 is an example of a user interface generated by the system of FIG.1 for receiving an image according to some aspects of the presentdisclosure.

FIG. 9 is an example of a user interface generated by the system of FIG.1 for displaying an approval status according to some aspects of thepresent disclosure.

FIG. 10 is an example of a user interface generated by the system ofFIG. 1 for displaying an approved status according to some aspects ofthe present disclosure.

FIG. 11 is a flow chat depicting a process for approving a physical carddesign using the card-personalization system of FIG. 2 according to someaspects of the present disclosure.

FIG. 12 is a flow chart depicting a process for generating apersonalized card using the card-personalization system of FIG. 2according to some aspects of the present disclosure.

DETAILED DESCRIPTION

Certain aspects and features of the present disclosure relate to acard-personalization system accessible by a user device from any ofmultiple network resources or channels using a unique user code that isassociated with both authentication information for thecard-personalization system and a status of the user in acard-personalization process. The card-personalization system mayinclude a personalization engine configured to allow a user topersonalize a physical card that may be used for transactions. Thecard-personalization system may assign the user a user code. The usercode may be a random set of alphanumeric characters and may beindependent of other user-specific authentication information, such asusernames, passwords, or personal identification numbers chosen by orprovided to the user for use in connection with the entity issuing thecard. The user code may be used to authenticate the user to accesspersonal or sensitive information associated with personalizing thephysical card. In some aspects, personalizing the physical card mayinclude a disjointed, multi-step process requiring selection of an imageby the user, multiple steps in a process for generating the physicalcard by personalization system. The user code used to authenticate theuser on the card-personalization system may also be used to identify theuser's position in the process for personalizing the physical card.

In some aspects, the user code assigned to the user may be stored in adatabase of the card-personalization system. The database may alsoinclude user information known by the card-issuing entity andcorresponding to the user (e.g., name, address, etc.). The database mayalso include a status identifier corresponding to different steps in thecard-personalization process. In some aspects, the database may storethe user code and the status identifier in a manner that associates theuser code and the status identifier with the user informationcorresponding to the user.

The physical cards personalized using a card-personalization system,according to some aspects, may be issued to or purchased by a user forconducting particular transactions. One example of a physical card thatmay be personalized and generated using a card-personalization system isa payment card, such as a debit card, credit card, or stored value card,associated with a user account and used to pay for goods or servicesfrom a user account. Another example of a physical card is an automatedteller machine (“ATM”) card associated with a user account and used toperform deposit and withdrawal transactions into and from the useraccount. Other non-limiting examples of physical cards that may bepersonalized using a card-personalization system include gift cards,calling card, rewards cards, etc.) In certain instances, a card-issuingentity may allow a user to personalize a physical card. In one example,the user may be allowed to upload or to select an image to be placed onthe card. The image may be a personal image provided by the user, astock image selected by the user from a gallery of images provided bythe card-issuing entity, or a previously stored image that thecard-issuing entity associates with the user (e.g., a securityphotograph). The card-personalization system may be accessible to theuser on a network via a network resource.

In some aspects, a network platform may include multiple networkresources linked to, or otherwise allowing access to, thecard-personalization system. The card-personalization system accordingto some aspects may assign a user code to a user and may use the usercode to authenticate the user on the system from any of the points ofaccess to the card-personalization system from the network resources.Also, the card-personalization system may also use the user code todetermine the user's position in the card-personalization process. Insome aspects, using the user code to both authenticate the use andidentify the user's status in the card-personalization process mayresult in fewer calls to the database for retrieving information. Also,using a user code separate from other user-specific authenticationinformation may allow a user to access the card-personalization systemfrom multiple access points on the network without concern for whetherthe network resource from which the user navigated to the systemrequired separate authentication information. Further, the dual purposesof the user code both to authenticate the user and determine a positionof the user in the card-personalization process may save processing timeand resources by reducing the number of user interfaces generated by thesystem and the number of data transfers between the user device and thesystem via the network.

These illustrative examples are provided to introduce the reader to thegeneral subject matter discussed here and are not intended to limit thescope of the disclosed concepts. The following sections describe variousadditional aspects and examples with reference to the drawings in whichlike numerals indicate like elements, and directional descriptions areused to describe the illustrative examples but, like the illustrativeexamples, should not be used to limit the present disclosure. Thevarious figures described below depict examples of implementations forthe present disclosure, but should not be used to limit the presentdisclosure.

FIG. 1 is a block diagram depicting a network environment 100 foraccessing a card-personalization system 102 from multiple networkresources 104A-D according to some aspects of the present disclosure.The card-personalization system 102 includes a computer system forgenerating a personalized physical card issued to or purchased by theuser from a card-issuing entity. The card-personalization system 102 maybe a personalized or private network resource and may authenticate auser prior to allowing the user to generate the personalized physicalcard using the card-personalization system 102. The card-personalizationprocess may be a disjointed process including multiple, disparate stepsfor generating a personalized physical card. For example, an imageselected by the user may require a separate approval process fordetermining whether the image is appropriate for placement on the card.The image approval process may take into account factors such as theimage resolution, the image data size, whether the image is virus-free,whether the image is copyright protected, etc. The card-personalizationsystem 102 may associate a status identifier with the user to determinethe user's position in the process each time the user accesses thecard-personalization system 102 via the network 106.

The card-personalization system 102 is communicatively coupled to eachof the network resources 104A-D via a network 106. In some aspects, eachof the network resources 104A-D may serve as a point of access to thecard-personalization system 102 for a user via a user devicecommunicatively coupled to the network 106. For example, each of thenetwork resources 104A-D may include a link, option, or otherpoint-of-entry to the card-personalization system 102 via the network106. The network resources 104A-D include website resources 104Arepresenting one or more websites that may be located on a networkplatform hosted by the card-issuing entity. The website resources 104Amay include a combination of public resources that do not requireauthentication for a user to access and personalized resources thatcontain information sensitive to a user and requiring userauthentication to access. For example, the website resources 104A mayinclude a series of webpages to various products and services offeredfor sale by the card-issuing entity. The website resources 104A may eachinclude a hyperlink or other access point to the card-personalizationsystem 102. In one example, a user may navigate to thecard-personalization system 102 from a website resource 104A requiringauthentication. In this example, the user may have previously enteredauthentication information to access the website resource 104A prior tonavigating to the card-personalization system 102. In another example, auser may navigate to the card-personalization system 102 from a websiteresource 104 that is public and does not require authentication, so maynot have previously entered authentication information upon navigatingto the card-personalization system 102. The network resources 104A-Dalso includes portal resources 104B. The portal resources 104B mayrepresent one or more portal sites requiring user authentication toaccess. A user navigating to the card-personalization system 102 fromthe portal resources 104B may have previously entered authenticationinformation prior to navigating to the card-personalization system 102.

The network resources 104A-D also include an access point to thecard-personalization system 102 via a link included in an electronicmail message or a text message, message link 104C. For example, themessage link 104C may be a web link, such as a hyperlink or uniformresource locator (“URL”). In some aspects, the web link may include auser code allowing the user to be authenticated without requiringseparate entry of the user code to access the card-personalizationsystem 102. An email or text message containing the message link 104Cmay be provided to the user following a request from the user topersonalize a card. In some aspects, the message link 104C may beprovided when the request is not made via a network resource 104A-D. Forexample, the user request may be made at a user central location. Theuser central location may include, but is not limited to, abrick-and-mortar building where the user made an in-person request for apersonalized card, an interactive machine, such as an automated tellermachine (“ATM”) or self-service kiosk, a 24-hour accessible interactivevoice response (“IVR”) system, or a phone agent. Once the request ismade, the card-issuing entity may transmit a personalized email or textmessage to the user including a web link for accessing thecard-personalization system 102.

The network resources 104A-D also includes a mobile application 104D.The mobile application 104D may include a client-side application storedon a user device, such as a smartphone or personal digital assistant(“PDA”) device, and corresponding to a server-side application engine ofthe card-personalization system 102 or another network resource (e.g.,network resources 104A-C) that is communicatively coupled to thecard-personalization system 102 and hosted by a card-issuing entity. Themobile application 104D may access the card-personalization system 102via the network 106. In some aspects, the mobile application 104D mayrequire authentication information to access one of the networkresources 104A-C and may, indirectly access the card-personalizationsystem 102 via links or other options on the network resources 104A-C.In one example, a user may be required to enter authenticationinformation to access one of the network resources 104A-C prior tonavigating to the card-personalization system 102. In other aspects, themobile application 104D may be an application allowing direct access tothe card-personalization system 102 via the network 106 and dedicatedfor allowing the user to personalize and generate a physical card.

FIG. 2 is a block diagram depicting the card-personalization system 102of FIG. 1 according to some aspects of the present disclosure. Thecard-personalization system 102 includes a processing device 200, amemory device 202, and a bus 204 connecting the processing device 200 tothe memory device 202. The processing device 200 may execute one or moreoperations for personalizing a physical card. The processing device 200may execute instructions stored in the memory device 202 to perform theoperations. The processing device 200 may include one processing deviceor multiple processing devices. Non-limiting examples of the processingdevice 200 may include a field-programmable gate array, anapplication-specific integrated circuit (“ASIC”), and a microprocessor.The memory device 202 may include any type of storage device thatretains stored information when the powered off. For example, the memorymay be included in a database 206 that may be used to store informationand instructions. The database 206 may include one database or multipledatabases. Non-limiting examples of the memory device 202 includeelectrically erasable and programmable read-only memory, a flash memory,or any other type of non-volatile memory.

In some examples, at least a portion of the memory device 202 mayinclude a computer-readable medium from which the processing device 200can read instructions of the memory device 202. A computer-readablemedium may include electronic, optical, magnetic, or other storagedevices capable of providing the processing device 200 withcomputer-readable instructions or other program code. Non-limitingexamples of a computer-readable medium include magnetic disks, memorychips, read-only memory, random-access memory, an ASIC, a configuredprocessor, optical storage, or any other medium from which theprocessing device 200 may read instructions. The instructions mayinclude processor-specific instruction generated by a compiler or aninterpreter from code written in any suitable computer-programminglanguage, including, for example, C, C++, C #, COBOL, Java, etc. Theinstructions may include an application, such as a personalizationengine 208, that, when executed by the processing device 200, may causethe processing device 200 to generate a user interface or a series ofuser interfaces for allowing a user to input or select an image. Thedatabase 206 may store information received from a user via the userinterfaces generated by the personalization engine 208.

The card-personalization system 102 also includes a network interface210 coupled to the bus 204. The network interface 210 may be a networkcard or other device positioned in the card-personalization system 102to be communicatively coupled to the network 106 and to allow userdevices 212 to access the card-personalization system 102 via thenetwork 106. In some aspects, the user devices 212 may access thecard-personalization system 102 by connecting to a network resource104A-D of FIG. 1 via the network 106 and navigating to thecard-personalization system 102 from the network resource 104A-D. Thenetwork interface 210 may receive information from the user devices 212or other network resources (e.g., network resources 104A-D of FIG. 1 )over the network 106 and provide the information to thecard-personalization system 102. The network interface 210 may becommunicatively coupled to the database 206 via the bus 204 to transmitinformation received over the network 106 to the database 206. In oneexample, the personalization engine 208 may generate a user interface toreceive information (e.g., an image selection) from the user via theuser device 212 connected to the network 106. The user interface may betransmitted to the user device 212 over the network 106 via the networkinterface 210. The network interface 210 may receive the informationinput or selected by the user via the user interface and store theinformation in the database 206.

In some aspects, the database 206 may include additional informationassociated with the user. For example, the database 206 may includeuser-identifying information. In some aspects, the user-identifyinginformation may include account information corresponding to accounts ofthe user with the card-issuing entity. The user code may be associatedwith the account information in the database to allow thecard-personalization system 102 to authenticate the user using the usercode. In some aspects, the account information may include apersonalization plan having a subset of the account information that maybe used to generate the personalized card. For example, the accountinformation may include an account number, an expiration date for aphysical card, a user name, and other information that may be applied tothe physical card to generate the personalized card.

The card-personalization system 102 may also include a code generator214. The code generator 214 may include a computational device in thememory device 202. In some aspects, the code generator 214 may includealgorithms executable by the processing device 200 to generate a randomor pseudo-random sequence of alphanumeric characters that may be used asuser codes to authenticate a user to access the card-personalizationsystem 102. In some aspects, the code generator 214 may be used inresponse to a request from a user or system to assign a user code to theuser. The user code generated by the code generator 214 may be a uniqueidentifier for the user. The card-personalization system 102 may assignthe user code generated by the code generator 214 to a user by storingthe user code in the database 206 in a manner that associates the usercode with the user. Although the code generator 214 is shown as acomputational device of the memory device 202, the code generator 214may be implemented in the card-personalization system 102 as a physicaldevice connected to the processing device 200 and the database 206 viathe bus 204 without departing from the scope of the present disclosure.

The card-personalization system 102 may also include an image analyzer216. The image analyzer 216 may be a computational device in the memorydevice 202 configured to analyze an image to determine characteristicsor properties of the image. In some aspects, the image analyzer 216 mayinclude algorithms executable by the processing device 200 for executinginstructions to determine image properties, including, but not limitedto, resolution, size, sharpness, etc. In additional and alternativeaspects, the image analyzer may include an image comparison module thatmay be configured to compare images stored in the database 206 withother images accessible to the image analyzer 216. For example, theimage comparison module may include matching algorithms for selectingpoints on a stored image to compare or correlate to points on anotherimage. The image comparison device may be used to determine the subjectmatter of the image for identifying stored images within a restrictedsubject matter (e.g., lewd images, malicious images, copyrighted images,etc.). In other aspects, the image analyzer 216 may include instructionsto extract image properties stored as metadata in the image filecontaining the image.

In additional and alternative aspects, the card-personalization system102 may also be configured to require human analysis of images stored inthe database 206. The card-personalization system 102 is communicativelycoupled to an agent 218 via the network 106 that may receive an imagefor approving or rejecting the image based on determined imageguidelines or restrictions. In some aspects, the agent 218 may be anemployee, contractor, or agent of the card-issuing entity. The agent 218may be communicatively connected to the card-personalization system 102via the network 106 using a computing device. In some aspects, thememory device 202 may include additional instructions executable by theprocessing device 200 to cause the processing device 200 to generate areport including the image and the user code. For example, the reportmay include a number of images received by multiple different users andmay include the user codes for identifying the user to which each imageis associated. The use of the user code may allow the images to betransmitted between the card-personalization system 102 and the agent218 in a secure manner without compromising the identity of the user.The agent 218 may approve or reject each of the images and transmit theresults of the approval process back to the card-personalization system102 as an approval report including the results associated with the usercodes. In some aspects, the results may be stored in the database 206and associated with the user using the user code associated with theimage on the approval report. Although the agent 218 is described ascoupled to the card-personalization system 102 via the network 106, thecard-personalization system 102 and agent 218 may transmit informationvia any means without departing from the scope of the presentdisclosure. For example, the images and user code may be retrieved fromthe database 206 and stored on a storage device with that may betransported to the agent 218 for analysis. In another example, thereport may be printed and hardcopies of the images and user codes may betransported to the agent 218.

The card-personalization system 102 also includes a printing subsystem220. The printing subsystem 220 may include a printer configured toprint or otherwise apply an image onto a physical card. In some aspects,the printer may be configured to apply the image directly onto thephysical card. In other aspects, the printer may be configured to applythe image to a material that may be adhered to the physical card tocreate the personalized card. In some aspects, the printing subsystem220 may also include indention tools to create indentions in thephysical card that form alphanumeric characters corresponding to userinformation stored as a personalization plan in the database. Forexample, the indention tools may create indentions in the physical cardto apply a user name, account number, and expiration date onto the card.In some aspects, the printing subsystem 220 may also include additionaltools to personalize the card. For example, the printing subsystem 220may include mechanical tools to add a metallic strip onto the physicalcard or embed a chip into the physical card, as well as additional toolsto transfer user information (e.g., the account number) or otherinformation of the card-issuing entity into the metallic strip or chip.Although the printing subsystem 220 is shown in FIG. 2 as included inthe card-personalization system 102, the printing subsystem 220 may be asystem separate from the card-personalization system 102 withoutdeparting from the scope of the present disclosure. For example, theprinting subsystem 220 may be communicatively coupled to thecard-personalization system 102 via the network 106.

FIG. 3 is a block diagram depicting an example visualization of thedatabase 206 of FIG. 2 according to some aspects of the presentdisclosure. The database 206 may include user-identifying information,User ID 1-3, user codes associated with the user, User Code 1-3, statusidentifiers corresponding to a position of the user in thecard-personalization process, Status ID 1-3, and images inputted orselected by the user during the card-personalization process, Image 103.Although only identifying information, user codes, status identifiers,and images are described, the database 206 may store additionalinformation without departing from the scope of the present disclosure.

The identifying information associated with the user of thecard-personalization system 102 may include any informationcorresponding to the identity of the user. Non-limiting examples of theidentifying information include a name, an address, account numbers,social security numbers, and personal identification numbers. In someaspects, this information may be retrieved from other systems hosted bythe card-issuing entity and stored in the database 206 when the userrequests to personalize a physical card using the card-personalizationsystem 102 of FIG. 2 . In other aspects, the database 206 may be ashared database with the other systems and may include the identifyinginformation stored for purposes of accounts associated with the user orother activities initiated by the user using systems hosted by thecard-issuing entity. All or a portion of the identifying information maybe including in a personalization plan. The personalization plan mayinclude specific identifying information that may be included on thephysical card (e.g., the name, account number, expiration date, a storedsignature, etc.).

The user codes assigned to a user may be generated by the code generator214 of FIG. 2 and stored in the database 206. In some aspects, the usercodes may be assigned to the users by storing the user codes in thedatabase 206 in a manner that associates the user codes with the user.For example, FIG. 3 shows a visual representation of an example of usercodes stored in the database 206 in a table. Each row of in the tablemay represent a different user. Information stored in the same row maybe linked or otherwise associated together in the database 206. Forexample, User Id 1, User Code 1, Status ID 1, and Image 1 may all beassociated with a first user of the card-personalization system 102 ofFIG. 2 . User Id 2, User Code 2, Status ID 2, and Image 2 may beassociated with a second user of the card-personalization system 102.User Id 3, User Code 3, Status ID 3, and Image 3 may be associated witha third user of the card-personalization system 102. In some aspects,the database 206 may include a marker, or other indicator, with the userinformation, user code, and status identifier to link them together orwith the user.

The status identifier, Status Identifier 1-3, for each user maycorrespond to the respective user's position in the card-personalizationprocess. The status identifiers may be associated with the users toallow a user to resume the card-personalization process from apredetermined benchmark in the process at a later time. In some aspects,the card-personalization process may be disjointed and includepredetermined benchmark positions such as: (1) receiving a card design(e.g., an image), or a selection of a card design, from a user via aninput on a user interface, (2) storing the image in the database 206pending approval of the image, (3) a multi-tiered approval step,including (a) an automated approval process by the image analyzer 216and (b) a manual approval process by the agent 218, (3) storing approvalresults (e.g., approval or rejection) in the database 206, (4)transmitting the image and a personalization plan to the printingsubsystem 220 for generating the personalized card, and (5) pendingfurther action following a rejection of the image (e.g., returning tothe “selecting a card design” benchmark).

For example, a user may select an image for a physical card and submitthe image for approval by the card-personalization system 102. Theapproval may take a number of days, preventing the user from maintaininga secure connection to the card-personalization system 102 until thenext step in the process. The user may return to thecard-personalization system 102 and enter the user code. Based on theuser code, the status identifier associated with the user and user codemay cause a user interface to be generated displaying the position ofthe user in the card-personalization process.

FIGS. 4 and 5 are flow charts illustrating examples of processes thatmay be used to generate a personalized physical card using thecard-personalization system 102 of FIG. 2 . The processes are describedwith respect to the components described in FIGS. 1 and 2 unlessotherwise indicated, although other implementations are possible withoutdeparting from the scope of the present disclosure.

FIG. 4 is a flow chart depicting a process for assigning a user code forthe card-personalization system 102 of FIG. 2 according to some aspectsof the present disclosure.

In block 400, a user code is generated in response to receiving arequest to personalize a physical card. In some aspects, thecard-personalization system 102 may receive the request to personalizethe card as a request for a user code. For example, the request for auser code may be received from a user via a user device 212communicatively coupled to the card-personalization system 102 via thenetwork. In another example, the request for a user code may be receivedfrom an agent or other representative of the card-issuing entity onbehalf of the user in response to a user indicating a desire to generatea personalized card to the representative. In alternative and additionalaspects, the user may request to personalize a physical card prior torequesting a user code. For example, the card-personalization system 102may allow a user to select an image without requiring userauthentication or otherwise providing identifying information. The usermay subsequently be required to select or create an account and enteridentifying information that may be stored in the database 206. Thecard-personalization system 102 may cause the code generator 214 togenerate a random code that may serve as the user code for the user. Insome aspects, the user code may be a set of alphanumeric characters thatthe user may enter to authenticate the user on the card-personalizationsystem 102.

In block 402, the card-personalization system 102 may associate the usercode with a user. In some aspects, the user may be assigned a user codein response to a request for a user code as described in block 400. Inother aspects, the user may be assigned the user code in response to arequest for identifying information from the user subsequent to the userselecting an image for personalizing the card as described in block 400.In some aspects, the card-personalization system may associate the usercode with the user in the database. The card-personalization system 102may assign the user code to the user by storing the user code in thedatabase 206 in a manner that links or otherwise associates the usercode with other user-identifying information of the user. In someaspects, the card-personalization system 102 may include a link ormarker with the user code to associate the user code to the otheruser-identifying information in the database 206. In other aspects, thecard-personalization system 102 may store the user code on a same row ina table with the identifying information as illustrated by the database206 in FIG. 3 .

In block 404, the card-personalization system may transmit the user codeto the user. In some aspects, the card-personalization system 102 maytransmit the user code to an agent of the card-issuing entity. The agentmay transmit the user code to the user via an email. In other aspects,the card-personalization system 102 may generate one or more userinterfaces displaying the user code on a display of the user device 212used by the user to access the card-personalization system 102. Infurther aspects, the card-personalization system 102 may cause theprinting subsystem 220 to print the user code. The printed user code maybe transmitted to the user via mail or by hand from the card-issuingentity. After the card-personalization system 102 is received by theuser, the user may subsequently access the card-personalization system102 via the network 106 to generate a personalized physical card.

FIG. 5 is a flow chart depicting a process for authenticating a user todesign a physical card using the card-personalization system of FIG. 2according to some aspects of the present disclosure.

In block 500, the user code is received from the user. In some aspects,the personalization engine 208 may generate a user interface includingan input option to allow a user to input a user code assigned to theuser as described in the process of FIG. 4 . The user code may beentered and a signal corresponding to the user code may be transmittedto the card-personalization system 102 from the user device 212displaying the user interface over the network 106. Thecard-personalization system 102 may receive the signal via the networkinterface 210.

FIG. 6 is an example of a user interface 600 that may be generated bythe personalization engine 208 to receive the user code. The userinterface 600 includes an input option 602 that may be selected by auser via a selection tool of the user device 212. A user may enter theuser code into the input option 602 via a keyboard tool of the userdevice 212. The user may subsequently select the selection option 604labeled “Continue” subsequent to inputting the user code into the inputoption 602. In response to selecting the selection option 604, thesignal corresponding to the user code may be generated and transmittedto the card-personalization system 102 via the network 106.

Returning to FIG. 5 , in block 502, the user is authenticated using theuser code. In some aspects, the card-personalization system 102 maycompare the user code received by the user with a user code assigned tothe user in the database 206. Upon determining that the user codereceived in block 500 matches a user code stored in the database 206,the card-personalization system 102 may authenticate the user based onthe identifying information associated with the user code in thedatabase 206. In some aspects, the user may be authenticated for apredetermined amount of time to allow the user to navigate away from thecard-personalization system 102 to other network resources 104A-D andreturn to the card-personalization system 102 without requiring the userto reenter the user code. For example, the card-personalization system102 may transmit a cookie to the user device 212 of the user with aunique session identifier. In additional and alternative aspects, thecard-personalization system 102 may temporary store a timestamp in thedatabase 206 and associate the timestamp with the user. The timestampmay correspond to a time that the user was authenticated on thecard-personalization system 102 using the user code. Thecard-personalization system 102 may allow the user to remainauthenticated for a predetermined amount of time and may compare thecurrent time to the stored timestamp to determine whether theauthentication has expired.

In block 504, the card-personalization system 102 determines a positionof the user in the card-personalization process. In some aspects, thecard-personalization system 102 may determine the position of the userby retrieving a status identifier from the database 206 corresponding tothe user's position in the process. The status identifier may beassociated with the user code and may be retrieved from the database 206using the user code. In some aspects, the status identifier may beretrieved from the database 206 simultaneous with thecard-personalization system 102 authenticating the user using the usercode as described in block 502. In some aspects, the status identifiermay indicate whether the user is beginning the process to design a card,whether an image selected by the user is in the approval stage, whetherthe image is approved, or whether the image is rejected. Blocks 506-512may represent a process of the card-personalization system 102 that maybe implemented in response to a signal indicating that the user has notyet designed a card or that a selected image was rejected. Block 514 andblock 520 represent a process of the card-personalization system 102 inresponse to a signal indicating that a selected image is in an approvalstage or has been approved, respectively.

In block 506, one or more user interfaces is generated to allow a userto input or select an image for personalizing a physical card. In someaspects, the card-personalization system 102 may generate the userinterfaces in response to a determination that the user has not yetselected an image for the physical card. For example, the statusidentifier associated with the user in the database 206 may indicatethat the user has not started the card-personalization process or thatno image is saved in the database 206 or associated with the user. Inanother aspect, the card-personalization system 102 may generate theuser interfaces in response to a determination that an image previouslyselected by the user has been rejected. The user interfaces may allowthe user to restart the process and select a new image for the physicalcard.

In some aspects, the user interfaces may include one or more inputoptions to allow a user to upload or otherwise input an image stored onthe user device 212 of the user. In other aspects, the image may beselected from a list of images displayed to the user with selectionoptions for choosing the image. For example, the database 206 mayinclude a gallery of stock images corresponding to different themes(e.g., nature, animals, sports, art, etc.). The user interfaces maypresent the stock images to the user for selection of a desired imagefor the physical card.

FIG. 7 is an example of a user interface 700 for receiving a selectionof an image. The user interface 700 includes a set of options to allow auser to select the type of image for personalizing the physical card.The set of options includes a selection option 702 labeled “Gallery”that may be selected by the user via a selection tool of the user device212 to allow the user to select an image from a gallery of stock images.The options also include selection options 704, 706 labeled “Personal”and “Photo ID,” respectively. The selection option 704 may allow a userto upload an image stored on the user device 212 for personalizing thephysical card. In some aspects, the selection option 706 may allow auser to upload an image including the user's face or profile topersonalize the physical card.

Subsequent to the user selecting the selection option 702 to indicate adesire to choose an image from a gallery of stock images, the user mayselect an image from an image gallery 708 that includes thumbnails ofimages that may be selected by the user for personalizing the physicalcard. The image gallery 708 may correspond to a set of images related toa theme selected by the user via the pull-down menu 710 selection optionshown in FIG. 7 . For example, the pull-down menu 710 indicates a themeof images related to “Work of Art” and may cause the system 102 todisplay images related to known works of art. Subsequent to a selectionof an image from the image gallery 708, the user may select theselection option 712 labeled “Continue.” In response to a selection ofthe selection option 712, a signal may be generated and transmitted tothe system 702 to indicate the selected image.

FIG. 8 is an example of a user interface 800 that for receiving an imagefrom a user in response to a selection of the selection option 704labeled “Personal.” The user interface 800 may include a selectionoption 802 labeled “Choose File.” The user may select the selectionoption 802 via a selection tool of the user device 212. A window may bedisplayed to the user including one or more files stored on the userdevice 212 that may be selected by the user and uploaded, or transmittedto the system 102 as an image for the personalized card.

Returning to FIG. 5 , in block 508, the image is received. In someaspects, subsequent to a selection or input of an image, the signal maytransmit a signal corresponding to the selected image. For example, theimage may be uploaded by the user using a user device 212 displaying theuser interface 800 to cause the user device 212 to transmit a signalover the network 106 to the card-personalization system 102. In anotherexample, the image may be selected from a set of stock images displayedon the user interface 700. Selecting an image by the user may cause asignal to be transmitted over the network 106 to thecard-personalization system 102 representing the selected image (or theimage's location in the database 206).

In block 510, the status identifier is updated. For example, the statusidentifier may be modified or updated from an identifier indicating thatthe user has not yet selected an image to an identifier indicating thatthe image is entering the approval stage. The updated status identifiermay be stored in the database 206 and associated with the user. In someaspects, the previous identifier may be deleted from the database 206.

In block 512, the image is stored in the database 206. In some aspects,the image is stored in the database 206 with metadata corresponding toproperties of the image. In other aspects, the image may be stored inthe database 206 as a link to a copy of the image stored with a set ofstock images for presenting to the user. The image may be stored in amanner that associates the image with the user. For example, the imagemay be stored in a table of the database 206 on the same row asidentifying information, a user code, or a status identifier associatedwith the user. The card-personalization system 102 may subsequentlyretrieve the image from the database 206 to perform an approval processprior to generating a physical card including the selected image.

In subsequent visits to the card-personalization system 102 by the user,the card-personalization system 102 may determine (in block 504) thatthe image is in an approval stage and proceed to block 514. In block514, one or more user interfaces is generated to indicate that the imageis in the approval stage. In some aspects where the approval stageincludes multiple levels of approval, the user interfaces may indicate alevel of the approval stage for the image.

FIG. 9 is an example of a user interface 900 for displaying an approvalstatus of the image selected or input by the user. The user interfaceincludes a message 902 indicating that the image is in an approval stepin the card-design process and that, if approved, an estimated date ofdelivery of the personalized card. The user interface 900 also includesa preview 904 of the personalized card including the image selected bythe user.

In some aspects, the card-personalization system 102 may optionallyallow the user to cancel or retrieve the image in the approval stage andto select a new image for personalizing the physical card. Blocks 516and 518 are dashed blocks in FIG. 5 to indicate that the steps areoptional. In block 516, one or more user interfaces are generated andinclude one or more selection options to allow the user to change apreviously selected image. In some aspects, the user interfaces may bethe same user interfaces informing the user that the previously selectedimage is in the approval stage, as described in block 514. The selectionoption may include a hyperlink, button, or other option that isselectable by the user via the user device 212 used to access thecard-personalization system 102.

In block 518, a request to change the previously selected image isreceived. The request may correspond to the user's selection of theselection option described in block 516. In some aspects, a signal maybe generated in response to the selection of the selection optiondescribed in block 516 and transmitted to the card-personalizationsystem 102 to indicate the request to change the previously selectedimage. The card-personalization system 102 may proceed to block 506 andgenerate user interfaces to allow the user to input or select a newimage.

In block 520, the card-personalization system 102 generates one or moreuser interfaces indicating that the image selected by the user isapproved. In some aspects, the user interfaces may include additionalinformation corresponding to the personalized card. For example, theuser interface may include a preview of the personalized card and wheninformation corresponding to when the personalized card will beavailable to the user (e.g., an estimated shipping date, an estimateddelivery date, tracking information, a pick-up location, etc.). Forexample, FIG. 10 is an example of a user interface 1000 that includes amessage 1002 including an message indicating that the card designprocess is complete (e.g., that the image is approved or in a printingstep in the card-design process) with an estimated delivery date for thecard. The user interface 1000 also includes a preview 1004 of thepersonalized card including the image chosen by the user.

In some aspects, the user interfaces may optionally allow a user tocancel or retract the approved image and allow the user to select a newimage as described in blocks 516 and 518 of FIG. 5 . Returning to FIG. 5, in block 522, the card-personalization system 102 transmits the imageand user-user-identifying information stored in the database 206 (e.g.,a personalization plan including a name, account number, expirationdate, etc.) are transmitted to the printing subsystem 220 for generatingthe physical card.

In additional aspects, the steps for generating a personalized carddescribed in FIG. 5 may also include providing notification to the uservia the user device of a change in the status of the user in thecard-design process. For example, in response to a change in a statusidentifier corresponding to a step of the user in the card-designprocess, the system 102 may generate a message indicated the user'sstatus or next step in the process. In some aspects, the message may betransmitted to the user via an electronic mail message. In additionaland alternative aspects, the message may be transmitted by a textmessage, application alert, or other suitable message to inform the userof the status.

FIG. 11 is a flow chat depicting a process for approving a physical carddesign using the card-personalization system of FIG. 2 according to someaspects of the present disclosure. The process is described with respectto the components described in FIGS. 1 and 2 unless otherwise indicated,although other implementations are possible without departing from thescope of the present disclosure.

In block 1100, the image is received. In some aspects, the image isreceived from the database 206 in response to a retrieval call to thedatabase 206 for the image. In other aspects, the image is received fromthe user as described in block 508 of FIG. 5 .

In block 1102, the properties of the image are determined. In someaspects, image properties may be included as information stored in thedatabase 206 with the image. For example, metadata may be stored with orextracted from the image corresponding to properties of the image suchas size, resolution, contrast, etc. In other aspects, thecard-personalization system 102 may analyze the image to determine theimage properties using the image analyzer 216. For example, a key-pointmatching algorithm of the image analyzer 216 may be executed by theprocessing device 200 to determine a subject matter associated with theimage or if the image corresponds to copyrighted, lewd, or othermaterials objectionable to the card-issuing entity.

In block 1104, the image properties are compared to image requirements.The image requirements may include required properties determined by thecard-personalization system 102 or the card-issuing entity for the card.For example, the card-issuing entity may not allow physical cards to begenerated having images below a threshold resolution, outside of acertain size range, having text, or of a certain subject matter (e.g.,lewd, copyrighted material). The image analyzer 216 may compare theimage properties to the requirements to determine whether the imagemeets the requirements.

In block 1106, the card-personalization system 102 determines whetherthe image is pre-approved. The image may be pre-approved if thecomparison of the image properties to the image requirements describedin block 1104 indicates that the image meets each of the requirementsdetermined by the card-personalization system 102 or the card-issuingentity. For example, the image may be approved if the resolution of theimage is above the required threshold, within the required size range,and includes no text. In some examples, the image may not be approved inif the image is below the required threshold, too large or too small, orincludes text.

In block 1108, the card-personalization system 102 updates a statusidentifier associated with the image to indicate that the image isrejected. In block 1110, the card-personalization system 102,optionally, transmits the image to the agent 218 for final approval. Theagent 218 may be a representative of the card-issuing entity tasked withreviewing the images submitted to the card-personalization system 102 byusers. In some aspects, the card-personalization system 102 may transmitthe image to the agent via the network 106 or a communication linkbetween the card-personalization system 102. In other aspects, thecard-personalization system 102 may be transmitted to the system via adownload of the image from the card-personalization system 102 by theagent 218 (e.g., onto a disc, universal serial bus device, etc.). Inadditional aspects, the card-personalization system 102 may transmit theimage to the agent via the database 206. For example, thecard-personalization system 102 may include an indicator in the database206 associated with the user information or the image to indicate thatthe image has been pre-approved. The agent 218 may retrieve the imagefrom the database 206 for final approval.

In block 1112, the card-personalization system 102 may determine whetherthe image was approved by the agent 218. The card-personalization system102 may make this determination based on information received from theagent indicating whether the agent has approved the image. In someaspects, the approval information may be transmitted by the agent to thecard-personalization system 102 in a similar manner as the transmissionof the image to the agent from the card-personalization system 102(e.g., the network, USB, database 206, etc.). The card-personalizationsystem 102 may update the status identifier using a user code associatedwith the image to indicate that the image was rejected, as described inblock 1108, when the card-personalization system 102 determines that theagent 218 did not approve the image.

In block 1114, the card-personalization system 102 updates the statusidentifier to indicate that the image is approved or that the physicalcard is in the process of being generated. In some aspects, thecard-personalization system 102 may also update the status identifierassociated with the user or image in the database 206 when the image ispre-approved subsequent to the step described in block 1106. Subsequentto updating the status identifier, the card-personalization system 102may implement the steps described in blocks 520 or 522 to generate auser interface indicating that the image is approved or transmit theimage and a personalization plan to the printing subsystem 220,respectively.

FIG. 12 is a flow chart depicting a process for generating apersonalized card using the card-personalization system of FIG. 2according to some aspects of the present disclosure. The process isdescribed with respect to the components described in FIGS. 1 and 2unless otherwise indicated, although other implementations are possiblewithout departing from the scope of the present disclosure.

In block 1200, the image is received. In some aspects, the image may beretrieved by the processing device 200 from the database 206 in responseto a retrieval call to the database 206 for the image and transmitted tothe printing subsystem 220. In additional aspects, the image is receivedby the printing subsystem 220 with a request that the image be printedor otherwise applied to a physical card. The image may be received bythe printing subsystem 220 via the bus 204, or another communicationlink where the printing subsystem 220 is separate from thecard-personalization system 102.

In block 1202, a personalization plan is received. In some aspects, thepersonalization plan may be received simultaneously with the image asdescribed in block 1200. The personalization plan may include userinformation that may be applied to the physical card to generate thepersonalization card. The personalization plan may be stored in thedatabase 206 and associated with the user and the user code. In someaspects, the personalization plan may include a subset ofuser-identifying information stored in the database 206 and associatedwith the user. Non-limiting examples of information that may be includedin the personalization plan include a name of the user, an accountnumber, a stored signature, and a security photograph. Thepersonalization plan may also include an expiration date that may bedetermined based on a predetermined timeframe from the transmission ofthe personalization plan to the printing subsystem 220 (e.g., two years,four years). The personalization plan may also include additionalinformation that does not identify the user, such as informationassociated with the card-issuing entity or randomly generated forapplying to the personalization card (e.g., a security code, a prefixnumber identifying the card-issuing entity or type of physical card,etc.).

In block 1204, a physical card is received. The physical card may bemade of plastic or other rigid material suitable for storing informationto allow for a transaction. In some aspects, the physical card may bereceived prior to the card being tailored to meet the requirements of aparticular service or transaction. In other aspects, the step describedin block 1202 may be optional and the physical card may already besemi-tailored with user information and only require application of theimage to the physical card. For example, the card may contain a magneticstripe, an embedded computer chip, user-identifying information such asan account number, name, or another data storage unit that containssensitive information relevant to the service or transaction (e.g., anamount of funds or credit available to the user).

In block 1206, a personalized card is generated. In some aspects, theprinting subsystem 220 may apply the image and the personalization planto the physical card to create the personalized card. In one example,the image may be printed onto an adhesive film that is sized to beplaced onto the physical card to personalize the card. In other aspects,the printing subsystem may print the image directly onto the physicalcard. In additional and alternative aspects, the printing subsystem 220may engrave or otherwise create indentions on the physical card to applyinformation from the personalization plan on to the physical card. Forexample, the printing subsystem 220 may engrave a name, account number,and expiration date on to the physical card. In further aspects, theprinting subsystem 220 may also apply a magnetic strip or embedded chipincluding information from the personalization onto the physical card.

The foregoing description of the examples, including illustratedexamples, of the invention has been presented only for the purpose ofillustration and description and is not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Numerousmodifications, adaptations, and uses thereof will be apparent to thoseskilled in the art without departing from the scope of this invention.The illustrative examples described above are given to introduce thereader to the general subject matter discussed here and are not intendedto limit the scope of the disclosed concepts.

What is claimed is:
 1. A system comprising: a processing device; and amemory device that includes instructions that are executable by theprocessing device to cause the processing device to: generate agraphical user interface configured to assist in a process forpersonalizing a physical card, wherein the process is formed from aplurality of steps including (a) receiving a selection of an image froma user, (b) approving the image for compliance with predefined imagecriteria, and (c) initiating manufacturing of the physical card with theimage; receive the selection of the image from the user via a userdevice; subsequent to the user selecting the image and accessing anaccount: authenticate the user to continue the process; determine acurrent step of the user in the process based on a status identifierassociated with the user in a database; and update the graphical userinterface to reflect the current step of the user in the process;determine that the image is in an approval stage of the process in whichthe image is analyzed for compliance with the predefined image criteria;update the status identifier to indicate that the image is in theapproval stage; and in response to determining that the image isapproved in the approval stage, retrieve account informationcorresponding to the account of the user and electronically transmit theimage and the account information to a printing subsystem for generatinga personalized card with the image for the user, wherein the accountinformation includes an account number and a name of the user.
 2. Thesystem of claim 1, wherein the memory device further includesinstructions that are executable by the processing device to cause theprocessing device to update the graphical user interface to include amessage indicating the image is in the approval stage.
 3. The system ofclaim 1, wherein the memory device further includes instructions thatare executable by the processing device to cause the processing deviceto update the graphical user interface to include a message indicatingthe image has been rejected.
 4. The system of claim 1, wherein theapproval stage involves a manual inspection of the image by an agent,and wherein the memory device further includes instructions that areexecutable by the processing device to cause the processing device to:transmit a report to the agent to manually review the image; receive anapproval or a rejection of the image from the agent; and update thestatus identifier based on the approval or the rejection.
 5. The systemof claim 1, wherein the printing subsystem is configured to, subsequentto the image being approved in the approval stage: obtain the image;receive, from a secure location in memory, the account informationcorresponding to the account of the user; and apply the image and theaccount information to the physical card to generate the personalizedcard for use as a payment card.
 6. The system of claim 1, wherein theapproval stage involves analyzing the image for copyrighted material orsubject matter that does not comply with one or more predefined lewdnessstandards.
 7. The system of claim 1, wherein the memory device furtherincludes instructions that are executable by the processing device tocause the processing device to store relationships between a useridentifier for the user, a user code, the status identifier, and theimage in one or more databases.
 8. A method comprising: generating, by aprocessing device, a graphical user interface configured to assist in aprocess for personalizing a physical card, wherein the process is formedfrom a plurality of steps including (a) receiving a selection of animage from a user, (b) approving the image for compliance withpredefined image criteria, and (c) initiating manufacturing of thephysical card with the image; receiving, by the processing device, theselection of the image from the user via a user device; subsequent tothe user selecting the image and accessing an account: authenticating,by the processing device, the user to continue the process; determining,by the processing device, a current step of the user in the processbased on a status identifier associated with the user in a database; andupdating, by the processing device, the graphical user interface toreflect the current step of the user in the process; determining, by theprocessing device, that the image is in an approval stage of the processin which the image is analyzed for compliance with the predefined imagecriteria; updating, by the processing device, the status identifier toindicate that the image is in the approval stage; and in response todetermining that the image is approved in the approval stage,retrieving, by the processing device, account information correspondingto the account of the user and electronically transmitting the image andthe account information to a printing subsystem for generating apersonalized card with the image for the user, wherein the accountinformation includes an account number and a name of the user.
 9. Themethod of claim 8, further comprising updating the graphical userinterface to include a message indicating the image is in the approvalstage.
 10. The method of claim 8, further comprising updating thegraphical user interface to include a message indicating the image hasbeen rejected.
 11. The method of claim 8, wherein the approval stageinvolves a manual inspection of the image by an agent, and furthercomprising: transmitting a report to the agent to manually review theimage; receiving an approval or a rejection of the image from the agent;and updating the status identifier based on the approval or therejection.
 12. The method of claim 8, wherein the printing subsystem isconfigured to, subsequent to the image being approved in the approvalstage: obtain the image; receive, from a secure location in memory, theaccount information corresponding to the account of the user; and applythe image and the account information to the physical card to generatethe personalized card for use as a payment card.
 13. The method of claim8, wherein the approval stage involves analyzing the image forcopyrighted material or subject matter that does not comply with one ormore predefined lewdness standards.
 14. The method of claim 8, furthercomprising storing relationships between a user identifier for the user,a user code, the status identifier, and the image in one or moredatabases.
 15. A non-transitory computer-readable medium comprisingprogram code that is executable by a processing device to cause theprocessing device to: generate a graphical user interface configured toassist in a process for personalizing a physical card, wherein theprocess is formed from a plurality of steps including (a) receiving aselection of an image from a user, (b) approving the image forcompliance with predefined image criteria, and (c) initiatingmanufacturing of the physical card with the image; receive the selectionof the image from the user via a user device; subsequent to the userselecting the image and accessing an account: authenticate the user tocontinue the process; determine a current step of the user in theprocess based on a status identifier associated with the user in adatabase; and update the graphical user interface to reflect the currentstep of the user in the process; determine that the image is in anapproval stage of the process in which the image is analyzed forcompliance with the predefined image criteria; update the statusidentifier to indicate that the image is in the approval stage; and inresponse to determining that the image is approved in the approvalstage, retrieve account information corresponding to the account of theuser and electronically transmit the image and the account informationto a printing subsystem for generating a personalized card with theimage for the user, wherein the account information includes an accountnumber and a name of the user.
 16. The non-transitory computer-readablemedium of claim 15, further comprising program code that is executableby the processing device to cause the processing device to update thegraphical user interface to include a message indicating the image is inthe approval stage.
 17. The non-transitory computer-readable medium ofclaim 15, further comprising program code that is executable by theprocessing device to cause the processing device to update the graphicaluser interface to include a message indicating the image has beenrejected.
 18. The non-transitory computer-readable medium of claim 15,wherein the approval stage involves a manual inspection of the image byan agent, and further comprising program code that is executable by theprocessing device to cause the processing device to: transmit a reportto the agent to manually review the image; receive an approval or arejection of the image from the agent; and update the status identifierbased on the approval or the rejection.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the approval stageinvolves analyzing the image for copyrighted material or subject matterthat does not comply with one or more predefined lewdness standards. 20.The non-transitory computer-readable medium of claim 15, furthercomprising program code that is executable by the processing device tocause the processing device to store relationships between a useridentifier for the user, a user code, the status identifier, and theimage in one or more databases.